<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<title>Eclipse Corner</title>
<link rel="stylesheet" href="../default_style.css">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000">
<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
  <tr> 
    <td ALIGN=left width="80%"> 
      <p><font class=indextop>2.0 Freeze/Test/Fix<br>
        Master Schedule</font><br>
        <font class=indexsub> Updated frequently to reflect current status</font></p>
</td>
    <td width="20%"><img SRC="../images/howto_banner.jpg" align=center width="272" height="111"></td>
  </tr>
</table>
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr> 
    <td align=left valign=top colspan="2" bgcolor="#0080c0"><b><font face="Arial,Helvetica" color="#ffffff">Freeze 
      Status</font></b></td>
  </tr>
  <tr> 
    <td align=right valign=top width="2%"><img src="../images/Adarrow.gif" border=0 width="16" height="16"></td>
    <td width="98%"> 
      <p>The eclipse team now in the 2.0 &quot;lockdown&quot; process which involves 
        a sequence of freeze/test/fix passes. We welcome everyone to help us test 
        and fix eclipse in these final stages before we finish 2.0. To participate, 
        you need to track to the same schedule we do, test when we do, and get 
        your <a href="http://dev.eclipse.org/bugs/">bugs</a> logged in time for 
        them to be considered before the next freeze. It is critical that we all 
        test at the same time. At each freeze the &quot;bar&quot; is raised on 
        what is allowed to be changed, so windows of opportunity for fixing problems 
        are narrow. It is virtually impossible to track exactly to a plan this 
        detailed, so <i>we will update this schedule continuously to indicate 
        current status, and what we are testing.</i> Be warned - this plan *will* 
        change - check back frequently if you are participating with us. Bug reports 
        to <a href="http://dev.eclipse.org/bugs/">bugzilla</a>. Process comments 
        should be flagged on <a href="http://dev.eclipse.org/mailman/listinfo/eclipse-dev">eclipse-dev</a>.</p>
    </td>
  </tr>
  <tr> 
    <td align=right valign=top width="2%"><img src="../images/Adarrow.gif" border=0 width="16" height="16"></td>
    <td width="98%"> 
      <p><b><a href="testplans.html">Test Scenarios</a></b> - test scenarios to 
        help drive testing.</p>
    </td>
  </tr>
  <tr> 
    <td align=right valign=top width="2%"><img src="../images/Adarrow.gif" border=0 width="16" height="16"></td>
    <td width="98%"><b><font color="#FF0000">June 28 Status</font></b>: Since 
      version 1.0, eight months of hard work by the entire Eclipse community has 
      culminated in the release of version 2.0 of Eclipse. It is ready for download 
      <a href="http://download.eclipse.org/downloads" target="_top">here</a>. Without the support 
      and enthusiasm of the entire Eclipse community we could not have achieved 
      this. A big thank you to everyone in the newsgroups, on the mailings lists 
      and especially everyone who reported bugs in Bugzilla. 
      <p></p>
    </td>
  </tr>
</table>
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr> 
    <td align=left valign=top colspan="2" bgcolor="#0080c0"><b><font face="Arial,Helvetica" color="#ffffff">How 
      does it work?</font></b></td>
  </tr>
  <tr> 
    <td align=right valign=top width="2%"><img src="../images/Adarrow.gif" border=0 width="16" height="16"></td>
    <td width="98%"> 
      <p><b>Freeze</b> - Freeze time indicated is when the build starts. Target 
        is to have freeze candidate build available within 24 hours of freeze. 
        Getting a good, testable build may require multiple attempts in rapid 
        succession. Although we may have a build, it will not be declared &quot;the&quot; 
        freeze until the team validates the build and declares it good for testing. 
        We will keep respinning the build until freeze can be declared. It is 
        critical that we have enough time to do test passes. We will slide schedule 
        and use weekends as necessary if there are delays of more than 24 hours 
        in getting good freezes.</p>
    </td>
  </tr>
  <tr> 
    <td align=right valign=top width="2%"><img src="../images/Adarrow.gif" border=0 width="16" height="16"></td>
    <td width="98%"> 
      <p><b>Test</b> - After a freeze is declared, the full test pass begins on 
        the freeze build. Each full test pass lasts 3 days. Each component team 
        must have a test plan to ensure adequate coverage of function and platforms 
        and to ensure everyone knows what to do. Each team is expected to have 
        at least 75% of the team testing during every test pass. The rest of the 
        team will be triaging bugs, preparing candidate fixes for critical problems 
        coming in, or working on documentation. <i>Everyone is encouraged to participate 
        in test passes and log bug reports to <a href="http://dev.eclipse.org/bugs/">bugzilla</a>! 
        </i> If you uncover what you believe could be a serious or stop-ship problem, 
        or a regression from a previous build, please make this very clear in 
        the bug report. </p>
    </td>
  </tr>
  <tr> 
    <td align=right valign=top height="63" width="2%"><img src="../images/Adarrow.gif" border=0 width="16" height="16"></td>
    <td height="63" width="98%"> 
      <p><b>Fix</b> - At each successive freeze, the rules for what changes are 
        allowed to the codebase, and what checks are required, become more restrictive. 
        NOTE: The rules apply to both fixes and feature work - any changes to 
        the code. All committers for a component have the right to veto a change 
        (with an explanation) even after it has been released into the codebase. 
        If such a veto occurs, the change automatically comes out unless the explanation 
        is shown to be invalid or the vetoing committer's concerns are addressed. 
        An Architecture Team member who approves work, or a Committer who checks 
        a change and does not veto it, takes joint responsibility for the change 
        with the Committer who releases it, and is implicitly agreeing to personally 
        help fix any problem caused by the change. Any Committer for any Eclipse 
        Project component can perform the checking duties.</p>
    </td>
  </tr>
</table>
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr> 
    <td align=left valign=top colspan="2" bgcolor="#0080c0"><b><font face="Arial,Helvetica" color="#ffffff">Detailed 
      Schedule </font></b></td>
  </tr>
</table>
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr bgcolor="#FFFFFF"> 
    <td align=left valign=top colspan="3"><b><font face="Arial,Helvetica" color="#000000"><a name="F1"></a>Tue 
      May 21, 8:00am EST -- Freeze 1 (F1)</font></b></td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%"> 
      <p>Full Test pass:</p>
    </td>
    <td width="72%">Wed May 22, 8:00am EST - Fri May 24, 5:00pm EST</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Fix rule after F1:</td>
    <td width="72%">Component Lead must approve all work - no changes released 
      without approval</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Notification requirements:</td>
    <td width="72%">N/A</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Check required on changes:</td>
    <td width="72%">N/A - However code check recommended at Component Lead discretion</td>
  </tr>
</table>
<hr>
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr bgcolor="#FFFFFF"> 
    <td align=left valign=top colspan="3"><b><font face="Arial,Helvetica" color="#000000"><a name="F2"></a>Fri 
      May 31, 8:00am EST -- Freeze 2 (F2)</font></b></td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%"> 
      <p>Full Test pass:</p>
    </td>
    <td width="72%">Mon Jun 3, 8:00am EST - Wed Jun 5, 5:00pm EST</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Fix rule after F2:</td>
    <td width="72%">Component Lead + 1 Arch Team member must approve all work 
      - no changes released without approval</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Notification requirements:</td>
    <td width="72%">Intent to change must be announced to component mailing list</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Check required on changes:</td>
    <td width="72%">2nd Committer code check required, reporter verifies fix (where 
      possible)</td>
  </tr>
</table>
<hr>
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr bgcolor="#FFFFFF"> 
    <td align=left valign=top colspan="3"><b><font face="Arial,Helvetica" color="#000000"><a name="F3"></a>Wed 
      Jun 12, 8:00am EST -- Freeze 3 (F3)</font></b></td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%"> 
      <p>Verification Test pass:</p>
    </td>
    <td width="72%">Thu Jun 13, 8:00am EST - Mon Jun 17, 5:00pm EST</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Fix rule after F3:</td>
    <td width="72%">Architecture Team must approve all work</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Notification requirements:</td>
    <td width="72%">Intent to change must be announced to component mailing list</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Check required on changes:</td>
    <td width="72%">2nd and 3rd Committer code check required, reporter verifies 
      fix (where possible)</td>
  </tr>
</table>
<hr>
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr bgcolor="#FFFFFF"> 
    <td align=left valign=top colspan="3"><b><font face="Arial,Helvetica" color="#000000"><a name="GM"></a>Monday
      Jun 24, 8:00am EST -- Golden Master Candidate (GM/F4) - Final code and doc</font></b></td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%"> 
      <p>Verification Test pass:</p>
    </td>
    <td width="72%">Tue Jun 25, 8:00am EST - Thu Jun 27, 5:00pm EST</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Fix rule after GM:</td>
    <td width="72%">NO CHANGES UNLESS A SERIOUS REGRESSION IS FOUND</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Notification requirements:</td>
    <td width="72%">Intent to change must be announced to component mailing list</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Check required on changes:</td>
    <td width="72%">2nd and 3rd Committer code check required, reporter verifies 
      fix (where possible)</td>
  </tr>
</table>
<hr>
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr bgcolor="#FFFFFF"> 
    <td align=left valign=top colspan="3"><b><font color="#000000"><b><font face="Arial,Helvetica" color="#000000"><a name="Release"></a></font><font face="Arial,Helvetica">Fri 
      Jun 28, 8:00am EST</font></b></font> -- </b><font face="Arial,Helvetica" color="#000000"><b>Golden 
      Master Release</b></font><font color="#000000"><b><font face="Arial,Helvetica"> 
      (R2.0) - Final code and doc</font></b></font></td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%"> 
      <p>Verification Test pass:</p>
    </td>
    <td width="72%">N/A</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Fix rule after R2.0:</td>
    <td width="72%">NO CHANGES. FIXES AFTER THIS POINT ARE RELEASED WITH THE NEXT 
      SERVICE UPDATE.</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Notification requirements:</td>
    <td width="72%">N/A</td>
  </tr>
  <tr> 
    <td align=right valign=top width="3%">&nbsp;</td>
    <td width="25%">Check required on changes:</td>
    <td width="72%">N/A</td>
  </tr>
</table>
<p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy 
  policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms 
  of use</a>.</p>
</body>
</html>
